Context linked messaging system

ABSTRACT

The present application contemplates a method of providing a participant with traversable access to a local environmental context of a target. In preferred embodiments, a context engine accesses multiple views of the local environmental context and stitches together the multiple views to produce a digital, walkabout reality of the local environmental context. Upon a participant/recipient accessing a communication from a sender, the participant is able to use a portal during a viewing session to traverse the digital, walkabout reality associated with a target. It is contemplated that the target is physically located within the local environmental context.

FIELD OF THE INVENTION

The field of the invention is messaging systems.

BACKGROUND

With the increased computing power available in increasingly smallerdevices, virtual reality environments and augmented reality environmentscan be rendered through a variety of mediums. With the increaseddistribution and engagement with augmented reality and virtual realityenvironment, messages can provide much more context than messagingmediums provide today. Though one can attach files to emails, sendrecordings of one's surroundings, and live stream videos to otherdevices, current technologies fail to take advantage of the additionalmessaging functionalities that are possible with current augmentedand/or virtual reality technologies.

U.S. Pat. No. 8,814,691 to Haddick teaches a system that enablesaugmented reality based social interactions. In that system, users arerequired to sign in through a separate website, which then inserts theminto an online game that is viewed through a head-mounted eyepiece.Since Haddick requires the use of a head-mounted eyepiece, histechnology fails to allow augmented reality messaging to be performedthrough conventional computing devices.

US Patent Application Publication No. 2010/0049702 to Martinez teaches amessaging system in which context data is derived from relatively staticdata. For example, Martinez discloses that a sender's social mediacontacts, personal interests, and selected music can be included incontext messages. Martinez fails to contemplate attaching real-worldcontext, such as a live feed, to electronic messages.

U.S. Patent Application Publication No. 2017/0161382 to Oulmet teaches amethod of processing image data by receiving both environmental data andassociated capture time data. Oulmet contemplates adding metadata toephemeral messages to provide a recipient with static environmentalcontext of the message at the time of sending. Oulmet fails to takeadvantage of the increased computing power of current personal computingdevices that enable real-world context data to include augmented realityand/or virtual reality context.

Haddick, Martinez, Oulmet, and all other extrinsic materials discussedherein are incorporated by reference to the same extent as if eachindividual extrinsic material was specifically and individuallyindicated to be incorporated by reference. Where a definition or use ofa term in an incorporated reference is inconsistent or contrary to thedefinition of that term provided herein, the definition of that termprovided herein applies and the definition of that term in the referencedoes not apply.

Thus, there is still a need for mixed reality systems infrastructuresthat allow participants/recipients to access context data that is usedto construct a traversable, digital, walkabout reality.

SUMMARY OF THE INVENTION

Among other things, the inventive subject matter provides apparatus,systems, and methods in which emails, texts, and/or other communicationsare sent with non-static, real world context of the sender. For example,a message sent by a sender in a coffee shop might include images of thepatrons and interior of the coffee shop.

As defined herein, context data can include any contextual dataassociated with a real-world environment, an augmented realityenvironment, and a virtual environment of a sender.

Various resources, features, aspects and advantages of the inventivesubject matter will become more apparent from the following detaileddescription of preferred embodiments, along with the accompanyingdrawing figures in which like numerals represent like components.

The present invention advantageously provides enhanced contextassociated with augmented reality and virtual reality spaces inelectronic communications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment.

FIG. 2 is a schematic of a method of identifying an electronic messageand linking context data to a context message.

FIG. 3 is a schematic of a method of delivering a context message to arecipient and sending local environmental context based on a recipientrequest.

FIG. 4 depicts a block diagram of component of the server computerexecuting a context engine within the distributed data processingenvironment of FIG. 1.

FIG. 5A depicts one embodiment of an augmented reality view interfacelinked to a context message as context data.

FIG. 5B depicts one embodiment of functionality associated with aninteractive object in the augmented reality environment.

DETAILED DESCRIPTION

While the following description is drawn to a computer-based schedulingsystem, various alternative configurations are also deemed suitable andmay employ various computing devices including servers, interfaces,systems, databases, engines, controllers, or other types of computingdevices operating individually or collectively. One should appreciatethe computing devices comprise a processor configured to executesoftware instructions stored on a tangible, non-transitory computerreadable storage medium (e.g., hard drive, solid state drive, RAM,flash, ROM, etc.). The software instructions preferably configure thecomputing device to provide the roles, responsibilities, or otherfunctionality as discussed below with respect to the disclose apparatus.In especially preferred embodiments, the various servers, systems,databases, or interfaces exchange data using standardized protocols oralgorithms, possibly based on HTTP, HTTPS, AES, public-private keyexchanges, web service APIs, known financial transaction protocols, orother electronic information exchanging methods. Data exchangespreferably are conducted over a packet-switched network, the Internet,LAN, WAN, VPN, or other type of packet switched network.

One should appreciate that the disclosed systems and methods providemany advantageous technical effects including improving conventionalcommunications mediums by incorporating context into messages.

The following discussion provides many example embodiments of theinventive subject matter. Although each embodiment represents a singlecombination of inventive elements, the inventive subject matter isconsidered to include all possible combinations of the disclosedelements. Thus if one embodiment comprises elements A, B, and C, and asecond embodiment comprises elements B and D, then the inventive subjectmatter is also considered to include other remaining combinations of A,B, C, or D, even if not explicitly disclosed.

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment.

The term “distributed” as used herein describes a computer system thatincludes multiple, physically distinct devices that operate together asa single computer system. FIG. 1 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made by those skilledin the art without departing from the scope of the invention as recitedby the claims.

Distributed data processing environment 100 includes computing device104 and server computer 108, interconnected over network 102. Network102 can include, for example, a telecommunications network, a local areanetwork (LAN), a wide area network (WAN), such as the Internet, or acombination of the three, and can include wired, wireless, or fiberoptic connections. Network 102 can include one or more wired and/orwireless networks that are capable of receiving and transmitting data,voice, and/or video signals, including multimedia signals that includevoice, data, and video information. In general, network 102 can be anycombination of connections and protocols that will supportcommunications between computing device 104, server computer 108, andany other computing devices (not shown) within distributed dataprocessing environment 100.

It is contemplated that computing device 104 can be any programmableelectronic computing device capable of communicating with variouscomponents and devices within distributed data processing environment100, via network 102. It is further contemplated that computing device104 can execute machine readable program instructions and communicatewith any devices capable of communication wirelessly and/or through awired connection. Computing device 104 includes an instance of userinterface 106.

User interface 106 provides a user interface to context engine 110.Preferably, user interface 106 comprises a graphical user interface(GUI) or a web user interface (WUI) that can display one or more oftext, documents, web browser windows, user option, applicationinterfaces, and operational instructions. It is also contemplated thatuser interface can include information, such as, for example, graphics,texts, and sounds that a program presents to a user and the controlsequences that allow a user to control a program.

In some embodiments, user interface can be mobile application software.Mobile application software, or an “app,” is a computer program designedto run on smart phones, tablet computers, and any other mobile devices.

User interface 106 can allow a user to register with and configurecontext engine 110 (discussed in more detail below) to enable a user toaccess a mixed reality space. It is contemplated that user interface 106can allow a user to provide any information to context engine 110.

Server computer 108 can be a standalone computing device, a managementserver, a web server, a mobile computing device, or any other computingsystem capable of receiving, sending, and processing data.

It is contemplated that server computer 108 can include a servercomputing system that utilizes multiple computers as a server system,such as, for example, a cloud computing system.

In other embodiments, server computer 108 can be a computer systemutilizing clustered computers and components that act as a single poolof seamless resources when accessed within distributed data processingenvironment 100.

Database 112 is a repository for data used by context engine 110. In thedepicted embodiment, context engine 110 resides on server computer 108.However, database 112 can reside anywhere within a distributed dataprocessing environment provided that context engine 110 has access todatabase 112.

Data storage can be implemented with any type of data storage devicecapable of storing data and configuration files that can be accessed andutilized by server computer 108. Data storage devices can include, butare not limited to, database servers, hard disk drives, flash memory,and any combination thereof.

FIG. 2 is a schematic of a method of identifying an electronic messageand linking context data to a context message.

Context engine 110 identifies an electronic message (step 202).

As used herein, an electronic message can comprise any data transmittedover any transmission medium to a recipient. A recipient can be definedas any party that receives or is intended to receive the electronicmessage. In some embodiments, the recipient is also the sending party.For example, a sender of the electronic message can send an email tohim/herself for archiving.

It is contemplated that context engine 110 can use any one or moremethods of identifying electronic messages known in the art.

In one embodiment, context engine 110 executes program instructions thattrack the delivery and receipt of email using web tracking technologies.Web tracking technologies can include, but are not limited to, cookies,web beacons/pixel tags, ultrasound beacons, and browser fingerprinting.

For example, context engine 110 can use cookies to track user activitiesto determine when an electronic message is sent and received, as well asidentify the electronic message and its contents.

In another example, context engine 110 can identify an electronicmessage and actions associated with the electronic message based on apixel tag associated with the electronic message that enables contextengine 110 to determine when a recipient, among other action, receives,opens, and manipulates the electronic message.

In yet another example, context engine 110 can identify one or moreactions associated with an electronic message using an ultrasonicbeacon. More specifically, context engine 110 can cause an ultrasonicsound to be emitted from a sending device which can be tracked using oneor more microphones associated with the sending party to determine whichelectronic message was sent and the time it was sent. Additionally,context engine 110 can cause an ultrasonic sound to be emitted from areceiving device when the electronic message is opened and/ormanipulated in some way, which allows context engine 110 to identifywhich message was sent and which actions were taken by a recipient inresponse to receiving the electronic message.

In yet another example, context engine 110 can identify an electronicmessage being sent/received by fingerprinting the web activity of thesender when the user sends an electronic message. Context engine 110 canalso identify the recipient and conditions associated with theopening/closing/manipulation of data in the electronic message byfingerprinting the web activity of the recipient.

In another embodiment, context engine 110 runs clients in computingdevices 104 of a sender and a recipient, respectively. In doing so,context engine 110 can identify electronic message sent between the twoparties and/or messages sent to third parties. It is contemplated thatcontext engine 110 can execute advanced analytical functions associatedwith messages sent between computing devices 104 using clients.

It is contemplated that context engine 110 can also analyze the contentsof an electronic message in identifying the electronic message.

However, it is contemplated that context engine 110 can identifyelectronic messages, attributes of the electronic message, and actionsassociated with the electronic messages in any manner known in the art.

Context engine 110 retrieves message context associated with theelectronic message (step 204).

Message context can include any identifying information about a userassociated with an electronic message. For the purposes of thisapplication, the user can be a target, which comprises any one or moreentities associated with the message.

In some embodiments, the message context can be associated with a senderand/or a recipient. For the purposes of this application, the recipientcan be a participant. In embodiments where the recipient is aparticipant, there does not need to necessarily be a transmission ofmessages between the participant and the sender of the context message.For example, the participant can be a passive viewer watching a streamerpassively through a website interface.

The message context is contemplated to give context about a target. Atarget can include human users, non-human entities, and any combinationthereof. For example, a target can be a video game streamer that is thetarget of the message. In another example, the target can be a website.

Identifying information about a user can include, but is not limited to,information regarding a user's digital footprint, any execution ofprogram instructions caused by user, personal information about theuser, environmental information associated with a user, and any entitiesthat a user in connected to.

It is further contemplated that message context can include real worldcontext, virtual world context (e.g., video games, computer simulations,etc.), augmented reality context, and any combination thereof.

In one embodiment, context engine 110 retrieves a user's digitalfootprint as the message context. For example, context engine 110 canretrieve the browsing history and programs used within the last hour bythe user to retrieve the user's shopping history as context to anelectronic message containing the keywords “online”, “shopping”, and“opinion”. In a more specific example, context engine 110 can identifythat a user is preparing an electronic message about shopping for a newdress and analyze the user's browsing history and purchase history toprovide relevant context to a recipient.

In another embodiment, context engine 110 retrieves executed programinstructions associated with the user as message context. For example,context engine 110 can identify the last three video games that a userplayed, achievements unlocked by the user, and amount of time played foreach game as message context, in response to a user preparing anelectronic message requesting a time to play a game together with anonline friend. In another example, context engine 110 can identify thelast three text documents saved by a user as message context, inresponse to a user sending a message to a known work colleague.

In yet another embodiment, context engine 110 retrieves personalinformation about a user as message context. For example, context engine110 can identify a user's physical attributes including their height,weight, hair color, and eye color, in response to the user preparing anelectronic message sent to a second user on an online dating website. Inanother example, context engine 110 can identify a user's credentialsincluding personal qualifications, professional qualifications, and workhistory, in response to the user preparing an electronic message to apotential employer on a hiring website.

In alternative embodiments, a user can select one or more types ofinformation to provide as context to context engine 110. For example,context engine 110 can receive a selection of particular types of datato transfer from a sender to send to a recipient. In another example,context engine 110 can receive a selection of particular types ofinformation authorized by a recipient to receive from a sender. In yetanother example, context engine 110 can preselect the types ofinformation that can be attached to a context message. In yet anotherexample, context engine 110 can receive instructions from a third-partyprogram for particular types of data to transfer between recipients andsenders.

In augmented reality and virtual reality context, the message contextcan be presented via user interface 106 as an augmented reality and/orvirtual reality-based view of the message sender's environment.

It is further contemplated that the message context can have interactiveelements (represented three dimensionally or two dimensionally) thatallow a recipient to interact with one or more virtual objects shown inthe augmented or virtual reality environment. It is contemplated thatthe interactive objects can be implemented using any artificialintelligence and/or machine learning technologies known in the art. Inone example, context engine 110 can use a time-series classifier todetermine what topics a recipient is usually interested depending on thetime of day and day of week. Based on this analysis, context engine 110can present relevant interactive objects to the recipient. For example,context engine 110 can prioritize placing interactive virtual beersoutside of bars.

In a related example, context engine 110 can also use a supervisedlearning classifier to find patterns in common characteristics ofreal-world objects that the user is interested in. For example, contextengine 110 can identify that much of the bars that the recipient hasbeen interested in the past have been more dimly lit, associated withclassic rock and roll music, and establishments that are not trending.Based on this analysis, context engine 110 can place interactive objectsindicating the presence of a bar that fits the same description, whichin turn directs the recipient to dive bars instead of hip hop clubs.

For example, a recipient accessing the augmented reality can select andicon that zooms out of the augmented reality to show more context. Therecipient can then select an icon in user interface 106 to filter searchresults and request all participants in the shared reality within a halfmile radius of the recipient. The recipient can then select an avatarwithin depicted in user interface 106 and send the avatar a privatemessage.

In another example, a recipient accessing the augmented reality canselect an icon placed by a business outside of their augmented realitystorefront that plays a video about the history of the business.

In yet another example, a recipient can access a particular geolocationdepicted on a map and indicated to have large amounts of news worthactivity. Based on the indicated hot spot, the recipient can enter theaugmented reality space around the newsworthy occurrence to accessvarious views from individuals streaming different perspectives of thescene (e.g., multiple views of a protest).

In instances where a recipient selects a first avatar in the scene toview the augmented reality space through the lens of the selectedavatar, it is contemplated that the recipient can further portal intoanother augmented reality view of a second avatar that is depictedthrough the perspective of the first avatar. In this way, it iscontemplated that a recipient can continue to portal through todifferent experiences, perspectives, relationships, transactions,discoveries as many times as the user chooses to.

In one example, the selected avatar can accept the message by placingtheir finger on a smart phone capacitive touch screen over an incomingmessage icon for more than 2 seconds to accept the message.

In another example, the message can be shown to the selected avatarautomatically. In yet another example, the private message can contain arequest, such as an offer for sale, a request for a live video feed, anda request to be friends through a social media service.

Additionally, a recipient can traverse the augmented reality and/orvirtual reality. For example, a recipient can “walk about” an augmentedreality and move through the augmented reality to get a better view ofwhich other avatars are present in the augmented reality space.

For example, context engine 110 can retrieve a three dimensionalrepresentation of a bedroom surrounding a sender and incorporateinteractive elements. The interactive elements can be other avatarsrepresenting other users that are in the bedroom. In a more specificexample, the avatars can be clickable, such that clicking the avatarallows the recipient to view the same bedroom through the perspective ofa user that did not send the original message.

In another example, context engine 110 can retrieve a live feed from acamera associated with the sender. Cameras can include conventionalvideo cameras, 360° cameras, infrared cameras, and depth-sendingcameras. However, cameras are not limited to any particular embodiment,and can comprise any sensor that retrieves visual data. The live feedcan also include additional interactive elements, including, forexample, a live representation of other users of context engine 110based on their respective geolocations around the sender.

It is further contemplated that context engine 110 can access multipleviews of the local environmental context to stitch together to produce adigital, walkabout reality. Walkabout realities are contemplated toinclude, but are not limited to, augmented reality environments that areassociated with the local environmental context of a target of thecontext message.

For example, context engine 110 can access a webcam in front of a videogame streamer, a 360° camera located in the center of the streamer'sbedroom, and two cell phone cameras of friends in the bedroom. Usingimages captured by the various cameras, context engine 110 can stitchtogether the photos and create an augmented reality within which theparticipants can “walkabout”.

In preferred embodiments, context engine 110 accesses the multiplecameras to retrieve multiple views of a local environment in a viewingsession. A viewing session can include, but is not limited to, timeswhen a participant is accessing the context message and times when asender allows participants to access the local environmental context ofthe target. For example, context engine 110 can access multiple camerasin a target's local environment when a participant/recipient accessesthe electronic message.

In another example, context engine 11 can access multiple cameras in thetarget's local environment when a participant/recipient accesses contextdata associated with the electronic message, as discussed in furtherdetail below.

Context engine 110 creates context data based on the message context(step 206).

It is contemplated that context data can be any combination of datacontaining program instructions that are executable by a computerprocessor. For example, context data can include a link to a live videostream, a program instruction to initialize an application, a photo, oneor more media records, and application-specific program instruction.

In another embodiment, context data allows a recipient to enter thevirtual and/or augmented reality space of the sender. It is contemplatedthat the context data can be in the form of a portal that allows therecipient to access the local environmental context around asubject/target. For example, a recipient can access a live view fromcameras in proximity of the sender and additionally see an augmentedreality overlay from the perspective of a selected camera thatidentifies one or more individuals. In a more specific related example,the recipient can select a camera associated with a first person at amedical conference to view the context of a message. The recipient canthen select another camera of a second individual at the medicalconference and see the same conference from a different perspective. Ifthe recipient sees a professional acquaintance through the lens of thesecond individual, the recipient can tap an icon next to theprofessional acquaintance on user interface 106 to view the conferencethrough the acquaintance's perspective or initiate additionalinteractive functions (e.g., text messaging, video messaging, etc.).Additionally, it is contemplated that context data can allow therecipient to access an official medical conference stream to access oneor more event cameras.

In preferred embodiments, the context data constructs a digital,walkabout reality of the local environment of the target while thetarget is within the local environment. For example, the context dataincludes the real-time local environmental context of the target.However, the context data can comprise local environmental context withrapid-time, quick-time, and a slow-time delays. For the purposes of thisapplication, rapid-time is defined as context data that is updated withthe local environmental context at least three times over a one-minuteperiod. Quick-time is defined as context data that is updated with thelocal environmental context at least three times over a ten-minuteperiod. Slow-time is defined as context data that is updated at leastthree times over a thirty-minute period.

It is contemplated that context engine 110 can capture context data in acontinuous manner, an intermittent manner, or any combination thereof.It is further contemplated that context engine 110 captures context dataoutside the control of the participant. Outside the control of theparticipant is defined as the updating of the context data occursautonomously with respect to the participant for at least some portionof a viewing session. It is important to contrast the present inventiveconcept with services, such as Google Street View™ and similar services,which (1) do not update autonomously with respect to the participant forat least some portion of the viewing session and (2) does not constructa participant-accessible digital, walkabout reality while the target iswithin the local environmental context. Instead, these technologiescapture images and update the context data with much longer delays thandiscussed in the preceding paragraph.

It is contemplated that the augmented reality overlay can presentinformation in any manner known in the art, including, for example,showing textual data and graphical data (e.g., the name and picture of ashared social media contact between the sender and recipient.).

In some embodiments, context data is attached as a separate executablefile in a context message. For example, context data can be anattachment in a dialogue box of a messaging service that a recipient orsender can open at their discretion.

In another embodiment, context data is directly integrated into thecontext message. For example, context engine 110 can integrate a mediaelement into the message. In a more specific and related example,context engine 110 can integrate a video clip of the sender'ssurroundings and a map overview showing a live feed of the geolocationsof shared social media contacts within a predetermined proximity of thesender.

It is further contemplated that context data can include context aboutpurely virtual environments. For example, context data can be a sender'scurrent virtual environment in a video game that allows a recipient tosee a live stream of a game through the sender's perspective.

Context engine 110 links the context data to the electronic message tocreate context message (step 208).

In some embodiments, context data is attached as a separate executablefile in a context message. For example, context data can be anattachment in a dialogue box of a messaging service that a recipient orsender can open at their discretion.

In another embodiment, context engine 110 directly integrates contextdata into the context message. For example, context engine 110 canintegrate a media element into the message. In a more specific andrelated example, context engine 110 can integrate a video clip of thesender's surroundings and a map overview showing a live feed of thegeolocations of shared social media contacts within a predeterminedproximity of the sender.

FIG. 3 is a schematic of a method of delivering a context message to arecipient and sending local environmental context based on a recipientrequest.

Context engine 110 delivers the context message to a recipient (step302).

Context engine 110 can use any means known in the art to deliver thecontext message to a recipient. In preferred embodiments, context engine110 delivers the context message to the recipient over network 102. Inother embodiments, context engine 110 delivers the context messagethrough purely hardware-based communication channels.

Context engine 110 receives a request to access the context data from arequesting party (step 304).

It is contemplated that requests to access the context data can be inany form available in the art.

In some embodiments, context engine 110 receives a request to access thecontext data by an affirmative action from the recipient. For example,context engine 110 can receive a request from a context messagerecipient when the recipient opens an attachment in the context message.

In another embodiment, context engine 110 receives a request to accessthe context data automatically when a recipient opens the contextmessage. For example, context engine 110 can send a context messagecontaining text with a smaller screen automatically showing a live viewof a baseball game from the stadiums official feeds. In this example, itis further contemplated that the live view of the baseball game can showaugmented reality elements that identify particular players on the fieldand real-time tracking of ball-flight by highlighting the ball in redand showing a predicted flight path.

In another example, context engine 110 can send a context message onlycontaining stored program instructions that cause the context message tobe a live view from the camera of the sender upon opening.

In some examples, the stored program instruction can cause userinterface 106 to show an augmented reality view of the sender'ssurrounding with interactive elements included. The interactive elementscan include, but are not limited to, clickable icons, interactiveavatars, and contextual information associated with the message, andmessaging overlays.

In a more specific example, the stored program instructions can allow arecipient to view a 360° view of the sender's environment. Uponidentifying avatars associated with a friend, the recipient can clickthe avatar of the friend to view the same environment through thefriend's perspective. Additionally, the recipient can input a messagethrough user interface 106 and send the message to the friend.

In some examples, the recipient can send the friend a context messagethat allows the friend to access a 360° view of the recipient's bedroom.In yet other examples, the recipient can input a message through userinterface 106 and simultaneously send the same message to all of theavatars present in the sender's physical environment.

In alternative embodiments, the stored program instructions cause userinterface 106 to show a virtual view of a virtual environment associatedwith the sender. For example, the virtual environment can be an areasurrounding a sender's video game character in a game world. It iscontemplated that the virtual view of the virtual environment caninclude interactive elements that allow added functionality, such as thefunctions associated with interactive elements described above.

Context engine 110 determines whether the request meets anauthentication parameter (step 306)

Authentication parameters can include any rules or lack of rulesassociated with a requesting recipient in opening a context message.

For example, authentication parameters can include rules associated withapproved recipients, context data available to particular recipients,geolocation-based restrictions, formatting restrictions, and contextdata sharing restrictions. In some embodiments context engine 110requires a recipient to input a password before granting access to thecontext data.

In response to determining that the request meets the authenticationparameter (“YES” branch, decision block 308), context engine 110 sendscontents of context data to the recipient (step 310).

In response to determining that the request does not meet theauthentication parameter (“NO” branch, decision block 308), contextengine 110 ends.

FIG. 4 depicts a block diagram of components of the server computerexecuting context engine 110 within the distributed data processingenvironment of FIG. 1. FIG. 5 is not limited to the depicted embodiment.Any modification known in the art can be made to the depictedembodiment.

In one embodiment, the computer includes processor(s) 404, cache 414,memory 406, persistent storage 408, communications unit 410,input/output (I/O) interface(s) 412, and communications fabric 402.

Communications fabric 402 provides a communication medium between cache414, memory 406, persistent storage 408, communications unit 410, andI/O interface 412. Communications fabric 402 can include any means ofmoving data and/or control information between computer processors,system memory, peripheral devices, and any other hardware components.

Memory 406 and persistent storage 408 are computer readable storagemedia. As depicted, memory 406 can include any volatile or non-volatilecomputer storage media. For example, volatile memory can include dynamicrandom access memory and/or static random access memory. In anotherexample, non-volatile memory can include hard disk drives, solid statedrives, semiconductor storage devices, a read-only memory (ROM), anerasable programmable read-only memory (EPROM), a flash memory, and anyother storage medium that does not require a constant source of power toretain data.

In one embodiment, memory 406 and persistent storage 408 are randomaccess memory and a hard drive hardwired to computing device 104,respectively. For example, computing device 104 can be a computerexecuting the program instructions of context engine 110 communicativelycoupled to a solid state drive and DRAM.

In some embodiments, persistent storage 408 is removable. For example,persistent storage 408 can be a thumb drive or a card with embeddedintegrated circuits.

Communications unit 410 provides a medium for communicating with otherdata processing systems or devices, including data resources used bycomputing device 104. For example, communications unit 410 can comprisemultiple network interface cards. In another example, communicationsunit 410 can comprise physical and/or wireless communication links.

It is contemplated that context engine 110, database 112, and any otherprograms can be downloaded to persistent storage 408 usingcommunications unit 410.

In a preferred embodiment, communications unit 410 comprises a globalpositioning satellite (GPS) device, a cellular data networkcommunications device, and short to intermediate distance communicationsdevice (e.g., Bluetooth®, near-field communications, etc.). It iscontemplated that communications unit 410 allows computing device 104 tocommunicate with other computing devices 104 associated with otherusers.

Display 418 is contemplated to provide a mechanism to displayinformation from context engine 110 through computing device 104. Inpreferred embodiments, display 418 can have additional functionalities.For example, display 418 can be a pressure-based touch screen or acapacitive touch screen.

In yet other embodiments, display 418 can be any combination of sensoryoutput devices, such as, for example, a speaker that communicatesinformation to a user and/or a vibration/haptic feedback mechanism. Forexample, display 418 can be a combination of a touchscreen in thedashboard of a car, a voice command-based communication system, and avibrating bracelet worn by a user to communicate information through aseries of vibrations.

It is contemplated that display 418 does not need to be physicallyhardwired components and can, instead, be a collection of differentdevices that cooperatively communicate information to a user.

FIG. 5A depicts one exemplary augmented reality view interface linked toa context message as context data. Context message interface 500comprises first avatar 502, second avatar 504, social media icons 508,and navigation icons 510.

First avatar 502 and second avatar 504 can be represented in any mannerknown in the art. For example, first avatar 502 and second avatar 504can be partially picture-based, completely virtual, or completelypicture-based.

Navigational icons 510 can be any one or more two dimensional and/orthree dimensional interactive objects allowing a recipient to navigatean augmented reality and/or virtual reality environment.

Social media icons 508 can be any one or more interactive objects thatallows the recipient to connect to an entity in the augmented realityenvironment. Entities can include, but are not limited, people, objects,and places. For example, a recipient can connect to a business, aparticular individual, and a iconic piece of street art through contextmessage interface 500.

FIG. 5B depicts one embodiment of functionality associated with aninteractive object in the augmented reality environment. FIG. 5Bincludes a messaging interface 512 that allows the recipient to send atext message to one or more entities in the augmented realityenvironment. However, messaging interface 512 can include any messagingfunctionality available in the art. For example, the recipient canrecord an audio message or send a picture message.

It should be apparent to those skilled in the art that many moremodifications besides those already described are possible withoutdeparting from the inventive concepts herein. The inventive targetmatter, therefore, is not to be restricted except in the scope of theappended claims. Moreover, in interpreting both the specification andthe claims, all terms should be interpreted in the broadest possiblemanner consistent with the context. In particular, the terms “comprises”and “comprising” should be interpreted as referring to elements,components, or steps in a non-exclusive manner, indicating that thereferenced elements, components, or steps may be present, or utilized,or combined with other elements, components, or steps that are notexpressly referenced. Where the specification claims refers to at leastone of something selected from the group consisting of A, B, C . . . andN, the text should be interpreted as requiring only one element from thegroup, not A plus N, or B plus N, etc.

What is claimed is:
 1. A method of providing a participant withtraversable access to mixed reality representation (MRR) of a real-worldlocal environmental context of a first target, different from theparticipant, comprising: accessing multiple views of the MRR; stitchingtogether the multiple views of the MRR, wherein the MRR includes aportal to a second MRR of a second target; further to the participantaccessing a communication from a sender, enabling the participant to usethe portal during a viewing session to traverse the second MRR, whereinthe first MRR comprises at least one interactive element linked to thesecond MRR of the second target; updating the MRR of the first targetduring the session, while the first target is physically located withinthe real-world local environmental context, wherein the updating the MRRof the first target includes a current geolocation of the first target;and the participant can add to virtual objects and functionality to theMRR of the second target.
 2. The method of claim 1, wherein the senderis not the first target.
 3. The method of claim 1, wherein the localenvironmental context is a substantially current physical space aboutthe first target.
 4. The method of claim 3, wherein the localenvironmental context can include virtual objects.
 5. The method ofclaim 1, wherein the multiple views are sourced from at least one of astatic image and a video.
 6. The method of claim 1, wherein theparticipant can add to virtual objects and functionality to the MRR ofthe first target.
 7. The method of claim 1, wherein the participant canbe a player in a game.
 8. The method of claim 1, wherein the participantcan be one party in a digitally transmitted conversation.
 9. The methodof claim 1, wherein the participant is at least one of a human, anon-human, and a combination of human and non-human elements.
 10. Themethod of claim 1, wherein the portal can be associated with anon-digital medium.
 11. The method of claim 10, wherein the non-digitalmedium is a printed medium.
 12. The method of claim 1, wherein thetarget is at least one of a human, a non-human, and a combination ofhuman and non-human elements.